Update daily environment to use 8.7 SNAPSHOT#758
Conversation
|
This pull request does not have a backport label. Could you fix it @ofiriro3? 🙏
|
Cloudbeat CI 🤖Allure Report: http://csp-allure-reports.s3.amazonaws.com/allure_reports/cloudbeat/prs/758/index.html |
|
This pull request is now in conflicts. Could you fix it? 🙏 |
| "title": "Kubernetes Security Posture Management (KSPM)", | ||
| "version": "1.1.1" | ||
| "title": "Security Posture Management (CSPM/KSPM)", | ||
| "version": "1.2.10" |
There was a problem hiding this comment.
this version is not stable, no?
There was a problem hiding this comment.
As far as I know the broken integration is 1.2.11, but the integration will auto-upgrade to 1.2.11 after the deployment.
As far as I saw I got findings as usual, although the agent wasn't healthy (on 1.2.11).
Do you think it would be better to deploy @jeniawhite version? 1.2.12-next
oren-zohar
left a comment
There was a problem hiding this comment.
As developers, we would like that the daily environment to represent the current content in the main branch.
Main is 8.8, and if this is the idea, why not dynamically use the version from the branch?
| "title": "Kubernetes Security Posture Management (KSPM)", | ||
| "version": "1.1.1" | ||
| "title": "Security Posture Management (CSPM/KSPM)", | ||
| "version": "1.2.10" |
There was a problem hiding this comment.
As far as I know the broken integration is 1.2.11, but the integration will auto-upgrade to 1.2.11 after the deployment.
As far as I saw I got findings as usual, although the agent wasn't healthy (on 1.2.11).
Do you think it would be better to deploy @jeniawhite version? 1.2.12-next
Yes that is a valid option. I'll update the description here. This is a reference to an item I already created before: |
…ith-SNAPSHOT' into weekly-enviroment-vanilla-work-with-SNAPSHOT
Prerequisite
Summary of your changes
We would like to update the daily environment to use the 8.7 SNAPSHOT while using the stagging cloud environment.
In-depth
As developers, we would like that the daily environment to represent the current content in the
mainbranch.That way, we would be able to detect bugs earlier in the development process, bugs that may appear only after a few fetching cycles.
** Currently 8.8 SNAPSHOT is broken, so this PR will deploy 8.7 SNAPSHOT.
I created another ticket to replace the hard-coded version with the latest SNAPSHOT.
How to test

Currently, the flow is deployed using a dispatch workflow, meaning - you will need to apply it using GitHub actions.
You can apply the flow from my fork, using actions.
Please set the branch to
weekly-enviroment-vanilla-work-with-SNAPSHOTbefore running the dispatch workflow.A new environment should be created with the 8.7 SNAPSHOT version.
You will receive the credentials to a dedicated slack channel named
ofir-personal-channel.Expected behavior
staging.found.noofir-personal-channel.Related Issues
Depends On